-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitoring actions #418
Monitoring actions #418
Conversation
Terraform plan for tts-10x-atj-dev Plan: 0 to add, 2 to change, 0 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~ update in-place
Terraform will perform the following actions:
# cloudfoundry_app.tts-10x-atj-dev-server-doj_tts-10x-atj-dev-server-doj-app_380DB029 will be updated in-place
!~ resource "cloudfoundry_app" "tts-10x-atj-dev-server-doj_tts-10x-atj-dev-server-doj-app_380DB029" {
!~ docker_image = "ghcr.io/gsa-tts/forms/server-doj:1c9df5e5a97bc4e81aeb7124dec7c36aeda4dfee" -> "ghcr.io/gsa-tts/forms/server-doj:c3b6dd687daa2cafa733edaf918df45b65abfc90"
id = "8a9fc8b6-af5e-45a2-abb6-2c24ecbcdfaa"
name = "tts-10x-atj-dev-server-doj-app"
# (17 unchanged attributes hidden)
# (3 unchanged blocks hidden)
}
# cloudfoundry_app.tts-10x-atj-dev-server-kansas_tts-10x-atj-dev-server-kansas-app_337A9CF1 will be updated in-place
!~ resource "cloudfoundry_app" "tts-10x-atj-dev-server-kansas_tts-10x-atj-dev-server-kansas-app_337A9CF1" {
!~ docker_image = "ghcr.io/gsa-tts/forms/server-kansas:1c9df5e5a97bc4e81aeb7124dec7c36aeda4dfee" -> "ghcr.io/gsa-tts/forms/server-kansas:c3b6dd687daa2cafa733edaf918df45b65abfc90"
id = "e885e531-11b7-4906-9cc3-0ddf483868f5"
name = "tts-10x-atj-dev-server-kansas-app"
# (17 unchanged attributes hidden)
# (3 unchanged blocks hidden)
}
Plan: 0 to add, 2 to change, 0 to destroy. 📝 Plan generated in Post Terraform plan to PR comment #506 |
…SA-TTS/forms into feature/413-performance-budget
This reverts commit 9577975.
The monitor budget action is failing in this PR and that is expected for now. The reason is that the GH action will run the test on the branch with the PR, and then switch to main and try run the test again to see if our bundles have gotten bigger or smaller. The dependencies for the |
Rethinking this approach to simplify it a bit. |
Add guardrails as the application grows. This starts with a very conservative performance budget to make sure we don't grow our bundle sizes too far beyond where we're at currently.